In reading the Upgrade docs for 2007 to 2010 it talks about Legacy Host Names. I believe that I get the Idea of what they are trying to accomplish, but I think when I installed our 2007 server I Didn't do it quite right and we ended up using the name of the Server for all of the client connections. So when we use OWA, ActiveSync and Outlook we type in the actual name of the 2007 server. i.e. server-exch2007.domain.com So given that is the case when I create the legacy name one would assume I would be creating something like the machine name for the connection, and then using the Official name for the new 2010 server. Though since our official name for client access is the name of the old server I'm not sure how I should Proceed. There are only 150 mailboxes (100GB of Mail Data), and many of the users use Active Sync to a Phone and then about another 15% use iPads too. While on the road sales people will either use their phone or OWA. Should I create a new more official mail name and use that for 2010 and then keep the server-exch2007 name for the Legacy and then just reconfigure all of the Clients? Thanks, Scott<-

The current owa,activesync, OA (server-exch2007.domain.com) would point to Exchange 2010. The legacy url would point to 2007 servers. Users never use the legacy URL, they only use the server-exch2007.domain.com and 2010 will route to legacy URL if the mailbox is on Exchange 2007. What certificates have you aquired? For OWA, OA, EAS to work externally you would need 3 names in the certificates. XXX.domain.com, legacy.domian.com, autodiscover.domain.com if you need to aquire a cert then consider not using server name and move to an actual url like mail.domain.com.

I'd like to move away from the old servername (server-exch2007) and use something more standard like the mail.domain.com. So if that is the case should I just use the server-exch2007.domain.com as the Legacy and create the new 2010 with the mail.domain.com and then start moving the clients to the new server name? Thanks

You could do that if all users will be trained to use mail.domain.com. If a 2010 user out of habit uses the server-exch2007.domain.com, he will receive errors. The redirection works from 2010 to 2007, but not vice versa.

Great, so I think the Buck stops here with the old name. Might as well get with the program now and not wait a few more versions to change it expecially since it has the version in the name! I dont know if I have not gotten to this part yet in the Upgrade guid, but it talks about creating the Legacy name, got that as I'm keeping the old name. For the new name, should I create it and point it to the Old Server and make sure it all works with the old server. Or can I skip that part and create the new name and point it to the IP of the new server from the get go? Thanks,

Old name to old server - works. Create new name to 2010 server and test. No need to pint new name to old server.

Thank you for your help! I appreciate it!